>A short quote from an internal post which I'm currently re-working into a MSKB article:
>
>...If you repeat with SET DELETED ON, each query that was fully optimized will now show as partially optimized but the times are the same. It is usually better performance-wise to not create a DELETED() tag, even though it will cause the query to be only partially optimized if SET DELETED is ON.

Glad to hear there will be some better documentation forthcoming than what's around now, which is 100% "Pro-Deleted Index." I might add that there's nothing wrong with temporarily creating the DELETED tag to test optimization levels, then removing before final DB release...