You can profile sections of code yourself by reading
the 8253 timer
both before and after a block executes, then subtracting. Mail me if
you'd like some example code. The timer counts from 65535 down to 0
about 18.2 times every second; if the code you're profiling executes
in less than 55ms, then you can do your own microsecond-accurate
timing.
A good reference on how to do this is in Michael Abrash's Graphics
Programming Black Book, Chapter three[1]. BTW, the whole book is great
reading if you are interested in x86 optimization in the [345]86-era.
Regards,
--Frej
[1]
http://www.gamedev.net/reference/articles/article1698.asp