Users would be able to construct more meaningful audit queries if Envers had an option to store and query information about modifications of individual properties, e.g.:
getAuditReader().createQuery().forRevisionsOfEntity(clazz, false, false)
With such a query, user will get only those revisions of (clazz, id), that modified property with propertyName.
Currently, to achieve that, user have to retrieve and compare manually two revisions, which increases complexity and decreases performance.