No, code-wise, that should work just fine.
Conventionally, things like that are passed in as pointers, but the constructor is overloaded such that it can take references instead, like you're doing (with no functional difference).
The only thing I can think of would be modifying it to pass pointers.
Code:
myRobot(&victor1, &victor2),
But that really shouldn't fix anything...