Assigning pseudo-handles could be dangerous (assuming we are talking about CurrentProcess(), CurrentThread(), CurrentSession(), ???) because their meaning is context sensitive and that context could easily be changed without the user realizing the significance.

Maybe we should disallow assigning them with a recommendation that developers clone then (making them non-pseudo) before then can be stored in a ScopedHandle.

> Check if either of the bottom two bits are set

Or check for the small set of hard-coded values - it looks like -1, -2, and -3 are the only ones?

I'll dig around the kernel and see what I find. I see some checks for higher order bits running around with comparisons to the likes of -1.

Don't all handles operate in the context of the current process anyways? CurrentProcess() is less bad in that light. CurrentThread() is interesting. Anyone passing a handle to a process in a different session would need to call DuplicateHandle on that handle anyways.