Pulse timers can't be accurate by the nature of the pulses. It's a random number from XX to XXX (can't remember the specific seconds). My pulse timer just took the average of the min/max range and used that as the reset point anytime it detected a pulse. You could improve on this quite a bit by using a running average to make a best guess at the next pulse. IIRC the pulses will average around the midpoint over time.
The problem with the counters, as Deathravin said, is that the data is being updated continually (every second with mine) which makes SF leak memory like a stuck pig.
It must be hard to type with ghostcrawlers penis lodged in your ass. - g++