Since my post was deleted, I will just re-iterate the main points:
DRM 1.0 Forward Lock cannot prevent piracy because it requires the client to enforce the DRM. Any client that doesn't implement DRM 1.0 Forward Lock can trivially circumvent it. And, once one person circumvents it, that person can post it somewhere where *everybody* can install it just like they'd install any other SISX they find online.
Most newer Nokia phones (at least, S60 phones) support DRM 1.0 Separate Delivery which may be more secure when the decryption key is delivered over SMS. Intercepting OTA delivery via SMS is something few people are able to do. But, again, once one person does it, they can share it with everybody and anybody. And, E-series devices do not support Separate Delivery for some reason.
Even though every iPhone App Store application is available on the internet stripped of its DRM, users can't install them without jailbreaking their phone. Apple's iPhone DRM works because there is no way to install an app on a non-Jailbroken phone except using the App Store client, and because very few people are willing/able to jailbreak their phones. Because S60 has a much more open mechanism for installing applications, it isn't necessary to crack the firmware to install applications that weren't purchased from the store. In other words, the Apple mechanism requires everybody who wants to install the app to hack their firmware first, whereas the S60 (and Android, BTW) mechanism only requires one person to post an app online and anybody can install it w/ no effort on the end-user's part.
Some people have suggested a "dynamic registration server" system like Handango and RIM's Blackberry App World use. That kind of implementation suffers from exactly the same kinds of problems as OMA DRM 1.0 Forward Lock. It is pretty easy to remove the registration checks from an app and/or disable functions that require non-user-grantable capabilities. It isn't nearly as easy as circumventing OMA DRM 1.0 Forward Lock (which can be 100% automated) but anybody with a dissassembler can do it. The only way to prevent that would be to have the functionality that requires non-user-grantable capabilities as an integral part of the application.
I believe that the Ovi Store will have to operate much like the iTunes Music Store. Everything in the iTunes store is just a few clicks away, for free from multiple websites. iTunes caters to users who value the convenience of the iTunes Store more than they value their money. The Ovi Store will have to do the same. That is, we (publishers) have to target users who are unlikely to hunt around for illegal copies of apps. And, the Ovi Store needs to be more convenient than any other source for content it sells. And, just like the iTunes store, content pricing will have to be low enough to make it seems reasonable for the user to pay for it instead of getting it for free.