The behavior of nested conversations and explicit conversation IDs seems strange to me:
The *current* conversation ID is replaced with the explicit ID of a nested conversation before the nested conversation is actually created... So my root explicit converation ID always gets replaced by any explicit IDs defined by nested conversations...
Is this a bug, or what's the reasoning for this?
Yes, this is a bug, please report it in JIRA, thanks.