I use both, depending on what I'm looking for.
When using the default profiler, I mark the start and stop times an look for totals like script names and number of times ran. I found this to be a good lag indicator in a few folks PWs I've helped debug over the years. I.e., using simple math, I knew how many placeable, area or module wide heartbeats "should" be firing each round and compared it to actual results for a quick and dirty litmus test.
For just about anything else, I use the NWNX2 profiler though.