The 3 default built-in performance counters show garbage data about slimtune HOT 5 CLOSED

That...should not be happening. I'm not sure, I guess I'll keep an eye out for 
a repro.

If you have specific things I can test, or functions I should debug locally, 
just tell 
me.

Well the values in the Counters table shouldn't be negative (or even 
particularly
large), unless the original counter is reporting them that way. So the first 
thing to
do would be to verify that the graph is reporting the contents of the Counters 
table
correctly.

Beyond that, you'd have to see if the backend is really sending those bogus 
values,
which come from ClrProfiler::OnCounterTimer.

Oh, and there's no fix for this issue incoming until after 0.2.1 is out.

I've retooled the counters a bit to remove the crazy fixed point storage etc. 
Open a new issue if this shows up again.