While it doesn't answer your question...
I recommend not using the profiler. It's measuring something like processor time, rather than wall-clock time. The profiler doesn't account for long disk accesses, slow serial connections, memory teardown time, etc, etc. This ends up very misleading.
Depending on what you're trying to measure, instrumenting your code is usually a more accurate, if somewhat tedious, way of doing things.