The "Right" answer is apparently a little misleading here... According to BOL, there would be entries in the DMV, they would just have all counters set to 0.
Effectively, this would mean that the DMV DOES tell you something - it gives you a list of all the indexes used since the database itself was last shut down or detached.
But then maybe it's just unclear in the BOL article, and the rows really are all removed every time the service is started. Does anyone know? (I don't have 2005 handy to test...)
Tao: BOL is indeed misleading. You can try it if you have a test server at your disposal - run some queries, check that various indexes used show up in sys.dm_db_index_usage_stats, restart the server and then query sys.dm_db_index_usage_stats again.
You don't really get "no" information. You'll at least get a list of column names <g>. And you'll get an overview of what indexes were used during system startup. On my test database, startup apparently involved one scan of sysendpts and one scan of sysobjvalues.
If the server has some huge startup procedures, querying sys.dm_db-index_usage_stats right after a server restart might even be useful...
Nitpicking aside, this is a great question. Many people still don't know about this view. And judging by the distribution of answers, many people don't know that it's fllushed on restart either.
Edit: One more nitpick - this view is not available on versions prior to SQL Server 2005.
I was torn between (A) and (D). I chose (A) because the question said that the user began using the server. My mistake was to assume the query "sys.dm_db_index_usage_stats DMV" was NOT the first thing the user did. I assumed that they had actually did other things before this query was ran.
Steve: Once more (and than I'll drop this). BOL is confusingly worded. The counters are *NOT* reset. You don't need to reword the question (but adding a bit to the explanation in the answer wouldn't hurt).
Cycle a server and query the view if you don't believe me.