Timezone close, but still not right

The latest version of Antville has been a huge improvement on previous versions of Timezone, but I noticed the following;

1. My Timezone is set to "-10(Australia/Sydney)" for Sydney, Australia. The create date is correct but the time is an hour ahead of Sydney time. Sydney is currently 11 hours ahead with daylight savings of the UK (GMT). I do not know if Antville handles daylight savings but if it does it is an hour ahead and if it doesn't its 2 hours ahead. Is this a bug or is the Antville server time set incorrectly?.
2. The site.monthlist macro is working correctly for timezone although I haven't tested for end of month scenarios yet, although based on what happens above I suspect it will be an 1 to 2 hours out.
3. When I create a story for the first time story.modifytime is set to story.createtime value. Should story.modifytime only be set to a value when an existing story is *edited* for the first time?
4. In Preferences, the sample datetimestamp for long date format and short date format are no longer in timezone time. This sample datetimestamp is 11 hours behind the timezone time (story.createtime) while 10 hours behind Sydney's actual time. What is the sample date/time meant to represent? GMT time?
5. Stories on the frontpage are sorted by story.createtime in decending order not by story.modifytime in decending order. I realise "Recently modified" stories are sorted by story.modifytime in decending order. Is it correct to have frontpage *stories* (not comments) sorted by story.createtime instead of story.modifytime, especially when story.modifytime is set initially with the value of story.createtime?

Clarification on the use of story.modifytime macro will probably resolve the conflicting questions of 3 and 5.

I don't want to seem overcritical as this is a big improvement on previous timezone fixes, i.e. only an hour out if Timezone caters for daylight savings and 2 hours if not. Getting close, but no beer. I look forward to your response.