created_on timestamp's precision is capped to seconds

[niner]

DBIx::Class::AuditLog::Structure::ChangeSet seems to use DBIx::Class::TimeStamp to set the created_on timestamp. This way the timestamp is rounded to whole seconds instead of the micosecond precision PostgreSQL's timestamps can deliver. Also it records a different time than other timestamps in the transaction. The now() SQL function always reports the time at the start of the transaction. So the AuditLog's created_on timestamp would record the exact (to the microsecond) same time as other timestamps allowing better correlation and reduced confusion.

Please change it to actually let the database do its job.