ZIM interval object count is off when time is set to 0 and immediate is true

BREAK

We had used a 5 millisecond delay to call the interval if immediate is set. But if the interval time is less than 5 milliseconds then this messes up the count with 1 being set twice. We are going to patch this in ZIM 018... but it is possible that it might change results in your app if you rely on the wrong count.