I think AP ignores elevation data from the watch, and instead calculates it from your route by comparing with a digital elevation model. Anomalies have been noted before, presumably due to shortcomings in the model. I also suspect that there could be issues if you're doing something like running along the edge of a cliff, and small GPS errors make it look like you're repeatedly going up and down the cliff face, though maybe Ken has filters for that sort of thing.