About the closest you can get is:
1. Use VCM to ensure that audit settings are correct (system audit settings, and, in some cases, like Windows File System, audit settings on the objects themselves)
2. Set up collection filters for objects of interest and related audit log events
3. Set up scheduled collections to regularly collect these filters
4. You can now write reports or use the VCM console to look at audit events that ocurred coincidentally with changes
The audit events will tell you who made a change, though some of them can still be very cryptic to analyze. For instance, renaming or editing a file involves a sequence of events where only the first one includes the original file name, subsequent events are based on the file handle. You need the first event to know which file was associated with the handle, then you can link to the other events to get some idea of what happened to the file after the handle was obtained. Having VCM change events to tell you a bit more about the object (e.g. the MD5 hash and file size changed) makes it somewhat easier to make sense of the audit log data.