Again six Vesta objects are created, but now each one is a temporary, unnamed object. In spite of its sophistication, this version of the program is about as impractical as the previous version. But the the simple task as stated, the first program is still the best. Again, whether the Vesta class is sensible depends on the task. If the task is complicated, and the above program is just a small step toward a complete solution, then maybe the Vesta class is a good design.
Further sophistication is to include the iteration limit in the constructor.
This version of the Vesta class is more flexible than the previous version. It is probably better since it can be used for more situations than the previous. This further increases the flexibility of the class. This version seem more logical, as well as being more versatile. The number of times a message should be repeated should be a characteristic of the request, not an inherent characteristic of the object.