Changemanagement in Windows SharePoint Services v3/Microsoft Office Server 2007 Forms-Services and Workflows : Sharepoint

In Microsoft WSS v3 the new feature of adding Infopath Forms as items
and workflows to SharePoint Form Libraries:

http://farm1.static.flickr.com/177/4...4eb4f4.jpg?v=0

This can be established with the out of the box possibilities of WSS
v3. To a SharePoint FormLibrary (1) a InfopathForm (2) is added as
content type and a workflow (3) can be applied by normal
administration tasks.
In a normal lifecycle of an application updates of the components are
necessary. This can affect the InfopathForm, the Workflow or the
FormLibrary.
In this changemanagement process Microsoft seems to support the
following model:

http://farm1.static.flickr.com/156/4...b287a0.jpg?v=0

In a initial deployment (2) the SharePoint Library (1) gets the
Infopath-Form v1 as content type and the workflow v1 attached. After a
given time, the SharePoint Library contains items with where created
based on Infopath-Form v1 and controlled by the workflow v1 (3). There
are items, on which the workflow is already completed and items where
it's still running (4).
If with a second deployment after some time changes are applied to the
Infopath Form and/or the workflow (7), Microsofts concept is, that the
old items still use the old Infopath Form (v1) and, if there workflow
is not already completed, finish with the old workflow v1.
Only new items in the FormLibrary can use the new Infopath Form v2 and
are supposed to run with the new workflow v2 (8)
Thus, for a certain time, items with the old and the new workflows are
hosted by the SharePoint Library.
It seems, that Microsoft thinks about workflows as elements, that are
not running too long. In praxis, there are certainly scenarios, where
workflows have to run for long time, even years. In these scenarios,
it's not acceptable, that changes in forms and workflows are not
applied to items which are attached to long running workflows and by
that are open since very long time and stay open further on.
A scenario like the following should be implemented in this case:

http://farm1.static.flickr.com/168/4...7a35b2.jpg?v=0

The initial Deployment (1-3) and the behavior of the first items is
exactly like in the first scenario. But after the next Deployment (6)
the items attached to still running workflows should use the new
Infopath Form v2 if one is provided and the new workflow v2. New items
should of cause use the new Forms and the new workflow.
It seems, that a scenario like that can not be reached by standard
means of WSS v3 or MOSS 2007.
Questions:
a) Is a scenario with changing forms and workflows for items with
still open workflows somehow supported by Microsoft out of the box
features ?
b) If not, what are the best bets to implement a scenario like that ?
We think about ideas like:
- exporting data, upgrading the forms, libraries and workflows and
reimporting the data afterwards
- programmatically upgrading the workflows
- other ideas ?