In addition to the answer you linked, there's also a LabVIEW-based example that uses the RDTSC (ReaD TimeStamp Counter) instruction to query a counter that increments at CPU freq (or thereabouts, I don't know the raw gory details down at that low level).
It was intended for use under Pentium-based RT systems, but I recall using it under Windows as well. Here's a link.
Just keep in mind that the timing uncertainty for a chain of function calls under Windows may be orders of magnitude greater than the actual CPU usage time.
When I'm checking performance under Windows, I usually look for some type of average time over maybe 10000+ calls, depending on the thingy I'm benchmarking. Also note that sometimes performance during a benchmark can be significantly better than it is in normal use. The tight looping may keep a lot of things in a local cache and require many fewer than normal wait states for memory access.
Good luck! Despite the quirks and difficulties of performing benchmarks, it's still good to take your best shot at it.
-Kevin P.
ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
