You can't do this with a timer which fires every 10 minutes. Potentially the file could be unchanged for nearly 20 minutes before you would notice it.
Consider this example.
1 second after your timer triggers, the file changes. The next time the timer triggers, it notices that file has changed and thinks all is OK. 10 minutes later, the timer is triggered again and at that point the event is raised, 19 mins and 59 seconds after the file last changed.
It comes down to timer granularity. If you need 2 second granualarity then you need to fire the timer every second.
What I would do is fire the trigger as often as possible and check the file, noting its last modified time. If the difference in time is > 10 mins, fire an event.
The frequency is up to you, but you may need to consider network traffic if the file is on a share.
Also, before you note the time, try to open the file in exclusive mode. If the file is currently being written you probably want to wait until the write is complete before checking any file modified times.
Chaz