update counter before triggering latch

as mentioned in #383

rx.concurrency.TestSchedulers.testSchedulingWithDueTime

is flaky because there is a race-condition where the test can assert the counter value before it is updated. fix is just to update the counter before releasing the latch.