A run's billable quantities, already split into the buckets a price unit type prices
separately. The numbers are in the driver's own BasePriceUnitType.UnitKind — tokens for
the token drivers, seconds for the time drivers, images for the per-image driver — which is why
the fields are named for their role rather than for tokens.
The cache buckets are meaningful only for token pricing; continuous-media drivers ignore them.
A run's billable quantities, already split into the buckets a price unit type prices separately. The numbers are in the driver's own BasePriceUnitType.UnitKind — tokens for the token drivers, seconds for the time drivers, images for the per-image driver — which is why the fields are named for their role rather than for tokens.
The cache buckets are meaningful only for token pricing; continuous-media drivers ignore them.