Hi @throup , welcome to the community, and thanks for reporting!
I could reproduce your example and confirm that we should see it as an issue. While the code still works when replacing a SequencedCollection parameter with Collection (note that the order would still be preserved; that’s a different use-case from instantiation, where such a replacement indeed would introduce a bug), it makes the intent of the developer clear that order is significant, even if no API specific to element order is used.