Fix for if you advance the TestableScheduler forward, then just call .tick(), an exception would be thrown
Instead if you advance the scheduler faster than realtime, subsequent calls to .tick() will tick for the LAST executed time, unless real time ends up advancing further than the scheduler was previously advanced.
That way you can execute things on the scheduler, and just run .tick() to call them (it's a minor case, I know)