I am not sure if this answers the original question....
VTune will certainly show an estimate of the total time spent executing a function, but I don't think that it tracks the number of times the function was called while the measurements were occurring. Since VTune uses a "sampling" methodology, a particular function will be sampled 0, 1, or more times per function execution -- mostly depending on how long the function executes.
If you run the measurements for the duration of the program execution and happen to know how many times the function was called, then you can divide the estimated total time for the function from VTune by the number of executions that you think happened to get the average time per function invocation.
The Intel C compiler has an option "-finstrument-functions" to generate "wrapper" calls at the entry and exit of each function. These can be used to collect statistics on function calls, including timers or performance counters, and provide both the function address and the call site address so that you can build call trees. This instrumentation disables function inlining, unless you instrument a function with a magical "__attribute__((__no_instrument_function__))" annotation. In that case the function will be eligible for inlining, but inlined copies will not generate instrumentation calls.....
