I have successfully used SQL's native auditing features. The only set-back I found was the location for the data (you can only choose "File", Windows "Security Log" or Windows "Application Log"). I would have preferred the data being stored in a table in a database on the instance. We opted for the "File" destination but this can be a bit tricky to maintain (and query) especially if you manage 100+ SQL instances.