One way is to specify the index in your debugger. Like arrayname[105] - that should give you the exact value at that index.
If yours were fixed length arrays, getting the value of a range would not be difficult. The debugger would then provide a small + sign beside your array object in the quick watch, and you could expand it to see all the elements.
But with free pointers, the debugger cannot do that. Becasue it does not know the length of the array. And Microsoft has taken a very tight fisted approach towards accessing out of bounds values, even in read only mode by the debugger - so it does not take any risk.
If you are so hell bent on seeing the values of a range, you have to do some little extra work dude:
Option A: Use the managed framework and declare an arraylist object, load it using your native array specifying the length. Your debugger will instantly show all the elements of the array list object expandable/ collapsible with a + sign
Option B: Write them down to a file on the hard disk ([index]:[value] format), open and inspect the file while debugging.
Option C: Declare a test only fixed length array (that you can comment later on), copy the contents of the native pointer array to it, and let the debugger do the rest.
Option D, E, F, ...: Give it up. There are better things to do in life.