While others may advise against it, I use a server side profile trace that runs continuously on the server (see to automatically start each time the MSSQL service is started). Naturally with all traces you need to be careful not to overload the server so we use carefully calculated filters to minimize the impact on the server.

For instance, setting the trace to only include the columns you are interested in tracking, setting other column filters i.e (tracking only certain sql logins who may be executing the procs, or perhaps set a minimum number of reads to track - say when a query's reads exceed 50,000 or say when the duration exceeds 5 seconds, and so forth.