I noticed same behaviour importing multiple keys in a row into the QT wallet. There must be a bug in the QT client.
You have to keep the timely order (according to "timereceived" in listtransactions) to get the correct coin generation timestamp shown in QT client, i.e. first import the key with the oldest coins, then the second oldest etc.
If you import a key with newer coins first and then one with older coins, the row with address of the older coins will show the timestamp of the newer coins, as it did in your screenshot.
I posted a question here
https://bitcointalk.org/index.php?topic=254226.0. I thought it was only related to immature coins, and since no many other coins have such a long maturity time, I guess not many people see this problem. Maybe it has nothing to do with whether the blocks being moved is mature or not?