It's the optimizer caching the query plan as a parameterized query. It's not re-planning the index lookup on every execution.
The parameter type is part of the cache identity, nvarchar and varchar would have two cache entries with possibly different plans.
The parameter type is part of the cache identity, nvarchar and varchar would have two cache entries with possibly different plans.