Can you post the full execution plan? You might be hitting the scan because of other things within the query, such as performing functions on the columns then using them as part of the WHERE clause.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning