The PriorityTicketHolder shifts the contention point of waiting for a ticket to the storage ticketing layer where the curop timer has started. When the SemaphoreTicketHolder is used, the contention point is in the networking layer which is outside of curop timer's tracking.

We should only consider time waiting for ticket as blocked time when it is also within curop timer's tracking ie. when PriorityTickerHolder is used.