SQL History - returning wrong statement if history is sorted

Question

I have searched the forum and not seen anything on this, but I have been getting the wrong SQL statement returned when I select Append/Replace.
I have statements going back to 12-Jan-06 (using 804 since 13-Jan-06, 796 since 12-Jan-06 and 715 last year), so I don't know if I have hit the aging limit or not (I think I counted 221 entries).
It seems to me that it works out the cursor position and then returns that statement number from the history - independently of resorting the history.
For example, if I sort from oldest to newest (based on timestamp) and then select the bottom statement (displays as newest) and Replace, I get the oldest statement in the worksheet. If I select the top statement (displays as oldest) and Replace, I get the newest statement in the worksheet.
This is further complicated by the fact that sorting on the Timestamp is doing an alpha-numeric sort, rather than a date sort. When sorting from oldest to newest, the bottom three timestamps are (in "oldest to newest" order) are:
1/23/06 10:58 AM
1/23/06 9:21 AM
1/23/06 9:31 AM
If I then remove the sorting, the statement returned is the correct one.

Answer 1

It was great to get the fix for the SQL History returning the right statement if sorted (we got it in v1184).
However v1215 still does a text sort on the TimeStamp column rather than a date sort, so 2PM comes before 9AM, etc.
Also, where is the format for the TimeStamp column coming from? As someone who doesn't live in the US and thinks that days should come before months in date formats (ie DD-Mon-YYYY), I am frustrated by yet another product that uses MM/DD/YY, despite my best efforts at telling it otherwise.