I found a particularly interesting use case for ticks not outlined here yet.
I was facing a scenario in my daemon where i wanted to use pcntl_fork and ensure that it happened precisely when i expected too but the symptoms where showing me otherwise.
The problem boils down into 2 parts, (1) How zend-ng (PHP7's new engine) collates C executions based on your compiled PHP directives, i.e. between each group of executions we have a 'tick', and (2) How resources are exposed to you in PHP, i.e. file descriptors are created on the O/S by the C code which may or may not be in the expected execution block when compiled from your code into C.
In simple terms, I opened a socket in the parent process and in a child process used it, simple right? well no, the resource in the child process wasn't always there as was expected and in all cases the parent process was not terminated (which normally explains why you lose access to open resources)
Forcing PHP to announce when a tick is done after one execution block actually forced zend-ng to be a little less efficient and ensure my blocks of execution weren running as expected.