Comment 2 for bug 1099966

We have included microsecond data (should be unique per token except in some fairly narrow scenarios). Further improvements are likely to require a lot of work for not a lot of benefit.

At this point I don't think we're seeing much of this error occurring either in test or real deployments, so I'm marking this as "Wont Fix". We can revisit this later if it turns out to resurface.