No hard feelings, I was just curious.
I don't recall a pricing problem of that type, certainly not in the past couple of months. But it's possible there was some temporary interruption in pricing data that could have reported something like that, but I couldn't find any transaction with a price that out of whack, so I just wanted to be sure I hadn't missed something in my database check.