NCover might be a good place to start; it profiles you're code to
ensure each method gets called, so it may keep track of those stats as
part of doing so.

Vai2000,

   You can try the CLR profiler:

http://www.microsoft.com/downloads/details.aspx?familyid=A362781C-3870-43BE-8926
-862B40AA0CD0&displaylang=en

I tried out four profilers a while ago for C# code:  DevPartner,
JetBrains dotTrace, AutomatedQA AQtime4, and red-gate's ANTS Profiler.
I thought red-gate's profiler was the best of those four by far.  

There are little things like better interface and easier to use and
such, but the bottom line was it quickly allowed me to see the
bottlenecks in my app and fix them, which is exactly what a profiler
is for.  :-)

http://redgate.com/products/ants_profiler/index.htm

One thing to note is that a new version of dotTrace has come out since
I did my testing, so perhaps their new one is a lot better.  I was
really surprised at dotTrace 'cause JetBrains, the company that makes
it, produces really good software otherwise and has excellent
developers and support.  

This site has a pretty big list of profilers too:

http://sharptoolbox.com/categories/profilers-debuggers

HTH,

Sam

------------------------------------------------------------
We're hiring!  B-Line Medical is seeking .NET
Developers for exciting positions in medical product
development in MD/DC.  Work with a variety of technologies
in a relaxed team environment.  See ads on Dice.com.