I have a large, computationally intensive application that spins off tasks using ThreadPool.QueueUserWorkItem. It is clear from hit counts and timing data that some of these tasks are being overlooked (execution completely ignored) in the reported results. In some cases, the same method is queued twice at different times and only one of the invocations contributes to the profiled results.
This is a .NET 2.0 application (C#). I am using Ants 184.108.40.206 on Windows XP Pro SP 2 and a dual-core machine.
I am not expecting you can do anything about this - don't have time to try and simplify the code to something I can share with you - but I wanted to report the issue.