Yup, but best practice is to mark it as UPROPERTY. And here I don’t see big deal to make pointer TArray as it holds pointers and don’t consume much memory.
Never use “new” or “delete” in UE4 or else you really need to (like instatiate non-UObject classes, which some editor apis require), let UE4 deal with,
TArray don’t need to be pointer because all it does is manage native array pointer so it’s kind of like making pointer of pointer and as Josh said reflection system does not support this kind of setup.
Also converted alkohol comment to anwser since… it’s answer and he is right Don’t be shy to post anwser even if you not sure,
You don’t need to allocate your heap memory for a TArray, just make it a member of your class. The garbage collector won’t be able to traverse that data structure and your AActors are going to get removed without your knowledge. Then crash