Not. Misses in the .NET api applications for the store were made either because the class simply could not work in the WinRT application, because it relied on inaccessible OS support, because it was possible to reduce some dead forests within the framework, or because the class was simply plain not makes sense in the Store app.
The absence of a SecureString greatly favors the “no sense” explanation. No attacker will ever encounter the problem of trying to dig a string from a few gigabytes of paging file data. Easy just download your application from the store and use the debugger in the comfort of your own home.
source share