When I want to do something similar to what you are talking-about, I have used a View. (eg. Rename the table from dbo.Table1 to dbo.Table1_Orig and create a View like dbo.Table1, which is a wrapper around the table and includes a SP call or inline-function or equiv). Views can behave like a table and often seem transparent to a user/app.
Otherwise, if your server is not really busy, you might want to consider using the SQL profiler, with a filter for that specific table, so it doesn't record gigs of queries. It will add some overhead onto a server (5%) but otherwise, it is pretty unobtrusive and easy to turn on/off. Some people are really wary of leaving Profiler on for very long, and some companies forbid pointing Profiler at a production DB. So be really careful if you try it. Keep an eye on it. You probably don't want to just leave it running for a few months. That would be evil.