This won't help you now, but another option available is to collect, and aggregate over time, the procedure calls by running a very lean server-side trace to capture queries run on the database in question. Then you can figure out which procedures are called, which queries are called, and by inference from those procs & queries, which tables are accessed.

But the data isn't built into the system, so you have to find a way to create it for yourself.

Another option for building the data would be regularly capture the information available in the cache by querying the DMV's such as sys.dm_exec_requests or sys.dm_exec_query_stats. You can then aggregate that information into a table somewhere and build up reports over time similar to what you would get from trace. However, since this information is only what is currently in the cache, you may miss queries or procedure calls depending on the frequency of your requests to the DMV and the volatility of the data in your cache.