Hello there!
I remember this being an issue before, but I haven’t had problems with this since I switched to 4.7.2.
I just did some tests with making a few stack objects, a few heap objects with pointers in a stack array and checking out some actors on the heap to see if I could see their properties as well, and all were readable.
I’m also using VS2013 albeit with Visual Assist X. I’m also running a development build, so some optimization goes on. But you can always turn that off with
#pragma optimize(“”, off)
YOUR FUNCTION
#pragma optimize(“”, on)
If you want to remove that from the equation.
Here is the test code I used to check out the stack/heap stuff, I just put it into some random callback function on my main character. All were inspectable.
TArray<FVector> Vectors;
Vectors.Add(FVector(0, 1, 2));
Vectors.Add(FVector(3, 4, 5));
TArray<FVector*> VectorPtrs;
VectorPtrs.Add(new FVector(6, 7, 8));
VectorPtrs.Add(new FVector(9, 10, 11));
FString TestString = FString(TEXT("Hello"));
FName TestName = FName("42yes");
If you still cannot get it to work, you always have the memory window (Debug->Windows->Memory->MemoryN), if you are getting the base pointer for lets say an array you can just inspect the memory where it points to and hopefully follow that to the data.
You can also do cool stuff with the immediate window (Debug->Windows->Immediate) to just dereference stuff and inspect their contents when you have hit a breakpoint. And you also of course have the Watch window (right click the variable you want to check out and do “Add watch”). You can do a lot of cool transformations in the watch window like if you have an array, you can add ,N to see only elements up to index N for example. So if I had an array called MyArray, I could write MyArray,2 in watch to see elements 0-1. There are other cool stuff you can do too, for example pointer arithmetic, so MyArray+50,5 to see the five objects from index 50 to 54. Be aware that they will be 0-indexed though xD.
If you can’t get rid of the problems, maybe these techniques can at least help you deal with them.
Do you have some sample code where this problem occurs for you, or is it everywhere? Maybe you just have some weird corner case and that’s why 
Best regards,