The TicketHolder and ScopedAdmissionPriority API allow writing code where the lifetime of ScopedAdmissionPriority does not match that of a Ticket issued while the ScopedAdmissionPriority was in scope. If the ScopedAdmissionPriority goes out of scope before the Ticket, the ticket will be released to pool with a different priority than when it was acquired.

To make sure this doesn't happen, the Ticket should record the priority its AdmissionContext had when the ticket was issued, and that priority should be used when releasing the ticket.