Of course, it depends on what you do, and how you want to do it.
The matter of fact is that, when you edit an event within the project window, you are just cutting up events, and after one minute you don’t remember which portion is where and why. (Unless the job is easy)
Suppose I am the director, and we have recorded a bunch of text with a gazillion retakes and alternative versions.
As a director, I ask you to play me a specific section. (Now you have to “guess” where this is located in your project.
As a director, I ask to let me hear the alternative takes of that one specific sentence.
As a director, I ask you to swap a specific portion with another
Now, unless you have put much effort into “documenting” your recording session, you will be in panic.
With my system -take a look at my screenshot-, I can drag/drop/audition any file that is been asked for within half a second. Defining regions is faster than cutting up events. you can even create regions from a cutted up-event. The extra mile you have to go is naming each region, but that is much less time consuming than documenting the project window. Actually, the naming of the regions is a simple copy/paste from the document the talent has used, the name of the talent and other information is added later by using the rename function.
Sure, it can’t be used for all editing jobs, depends on the workflow.
But pretty much anything that is recorded in one continious take, and has to be cut up later is worth considering this method. Take a another look at my screenshot, this is an example of a Radio promo. Talent has read several takes. (There is also a second/alternating voice involved, so they both have the same lines)
This is the basic work that is been done by an assitant. When the editor starts working on the promo, he just has to choose the takes and drop them in place. No more hassle of going through a long file to find what you need.