The only risk here is that someone at Microsoft might change it in the future. You could also just build your own wrapper around ExAcquireResourceExclusiveLite, in which case you are “future proof” (at least against this specific issue.)
Tony
Tony Mason
Consulting Partner
OSR Open Systems Resources, Inc.
http://www.osr.com