As of MySQL 5.6.4, released Dec 20, 2011, the TIMESTAMP data-type now supports 6-digit microseconds precision. The big question is whether or not the data-type maintained in the Envers REVINFO or user-defined revision-entity table should be aligned with that maintained in each audited entity's audit history table when the REVEND_TSTMP feature is enabled.