Sometimes I see code that uses a new allocation to set a Unity Vector2/3 with new values instead of Set(), unless I'm missing some setting of the compiler magically replacing that instruction with something else this is a very unoptimized way of doing so.
@djlink I’ve been using Unity for a couple of years and had no idea that Vector3.Set() existed. It’s always seemed frustratingly inefficient.