Your best option will be to use SQL Server Extended Events:
Using SQL Server 2008 Extended Events[
^]
I've used this to capture rogue uses running queries they shouldn't be. As I don't know what all your application does, I can't tell you which events you will need, but the documentation is really good on this.